Let's make sure our naming is consistent. This is how it is written on
the ESLint docs site.

Having the prefix makes it easier to quickly tell which commits were
generated. Has been helpful in local dev when generating multiple test
commits and needing to squash them down before pushing them up to
Github.

ESLint will return exit code 2 if something completely breaks during
parsing. Let's make sure that's exposed if we're looking for it.

Because the current file is blank, it was not causing the parsing issues
we are seeing with v1.0.0 and non-js files

Without this manual filtering, ESLint will attempt to lint files that
should be ignored (like ruby files). ESLint v9 has the `files` option in
the flat config, and earlier versions have the `--ext` CLI flag. Let's
aim for maximum compatibility and just ignore the files that don't end
in the extensions we want.

fix: Use extensions input to filter files passed to ESLint